Systems and methods for real-time updating of attributes of an area and status of devices within the area

ABSTRACT

A system described herein may generate visual representations of physical locations, such as floors of office buildings, outdoor areas, or other types of places. The visual representations may be based on a node map, which may be generated based on data received from user devices and/or by owners or proprietors of business or other types of locations. The node map, for a given place, may indicate features of the place, such as architectural features (e.g., doors, walls, or rooms), visible features (e.g., wall hangings, signs, or other landmarks), Radio Frequency (“RF”) footprint features, or other features. The node map may indicate the likelihood of a given user device moving from one node to another node, and these likelihoods may be used to generate navigation instructions.

CROSS-REFERENCE TO RELATED APPLICATION

This Application is a Continuation of co-pending U.S. patent applicationSer. No. 16/129,471, titled “SYSTEMS AND METHODS FOR REAL-TIME UPDATINGOF ATTRIBUTES OF AN AREA AND STATUS OF DEVICES WITHIN THE AREA,” filedSep. 12, 2018, the contents of which are hereby incorporated byreference.

BACKGROUND

Entities, such as corporations, schools, and institutions may havephysical facilities, such as offices, stores, or other buildings. Thesefacilities may be large, confusing, and/or otherwise difficult tonavigate. Additionally, individuals (e.g., staff, customers, etc.) maybe present within the facilities at different locations in differentcircumstances. For example, an employee may be seated in a conferenceroom one morning, and at a cubicle on a different floor in theafternoon. While it would technically be possible for such an employeeto manually update his/her status (e.g., by using a sign-in sheet,notifying a supervisor of his/her location, etc.), this technique isprone to errors, such as the employee forgetting to update his/herlocation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1E illustrate an example overview of one or more embodimentsdescribed herein;

FIGS. 2 and 3 illustrate example environments in which one or moreembodiments, described herein, may be implemented;

FIG. 4 illustrates example data that may be used by a Place AttributeInformation Repository (“PAIR”) in some embodiments;

FIGS. 5A and 5B illustrate example arrangements of a node map, which maybe stored by the PAIR of some embodiments;

FIG. 6 illustrates example data that may be used by a Real-TimeAssistance System (“RTAS”) in some embodiments;

FIG. 7 illustrates example communications between a User Equipment(“UE”), PAIR, RTAS, and user interface system of some embodiments;

FIG. 8 illustrates an example process for obtaining and presentingattribute information associated with a particular place;

FIG. 9 illustrates an example process for assisting a user in navigatinga place based on the node map and further based on real-time feedbackfrom the user (e.g., from a UE of the user), in accordance with someembodiments; and

FIG. 10 illustrates example components of one or more devices, accordingto one or more embodiments described herein.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements.

Some embodiments, described herein, may generate a representation (e.g.,a graphical representation, a logical representation, or some other typeof representation) of one or more places. As discussed herein, the term“place” refers to a given physical area, such as a room, a portion of afloor of a building, an entire floor of a building, multiple rooms orfloors of one or more buildings, or the like. In some embodiments, aplace may include physical boundaries, such as walls, doors, fences,barriers, etc.; while in some embodiments, a place may not includephysical boundaries (e.g., may be an arbitrarily defined region eitherindoors or outdoors).

The representation of a given place may be presented on a user equipment(“UE”), such as a mobile telephone, of a user who may be interested inthe place. For example, as shown in FIG. 1A, a visual representation(e.g., a Graphical User Interface (“GUI”) of a floor of a building(i.e., Floor 3 of “Building A,” in this example) may be presented on adisplay screen of a UE. The visual representation may include anoverhead “floor plan” view. The visual representation may indicatefeatures of the place, such as layout features of the place (e.g.,offices (i.e., Offices A-F, in this example), conference rooms (i.e.,Conference Rooms A and B, in this example), and walkways. The visualrepresentation may also indicate visual features of the place (e.g.,features that may be visually detected by a user or a device that isphysically present in the place), such as a sign hung on a wall. Thevisual representation of the place may also indicate WiFi networks thatare available to join (e.g., by listing the Service Set Identifier(“SSID”), and/or may indicate where network devices (e.g., WiFi accesspoints, routers, Bluetooth Low Energy (“BLE”) beacons, etc.) arelocated. As described below, the visual representation of a place may begenerated based on one or more data sources, such as a floor plan of abuilding, data collected by UEs that are present in the place, and/orother sources.

As further shown, the visual representation may include detailedattributes of some of the features of the place. For example, forconference rooms and flexible work spaces (shown in the figure as “Flexspaces,” which may be workspaces that can be dynamically allocated todifferent individuals at different times), the visual representation mayinclude an indicator that indicates whether the conference room or flexspace is available or occupied. For example, as shown, each conferenceroom or flex space may include a box that is either empty or contains an“X” (where an empty box indicates that the room is available, while an“X” denotes that the room is occupied). As another example, eachconference room or flex space is illustrated with differing levels ofshading, where a darker shade indicates that the room is occupied, and alighter shade indicates that the room is available. One or more of therooms may also include a label that shows the occupant(s) of the room.For example, Flex Space A includes a label showing that the occupant is“John S.,” while Flex Space C includes a label showing that the occupantis “Brian L.” As further shown in the figure, some of the rooms (e.g.,offices) may not be shaded (and/or may be shaded differently from roomsthat are available or occupied). This lack of shading (or differentshading) may denote that these rooms are not available for reserving.

The visual representation may further include an indicator (shown in thefigure as a star) that shows a current location of the UE itself. Asdiscussed below, the occupancy status (and/or the location of the UEitself) may be determined based on feedback received from UEs. Forinstance, location information received from a UE carried by John S. maybe used to determine that Flex Space A is occupied by John S.

The GUI shown in FIG. 1A may also include selectable options (e.g.,buttons), such as “Select a new place to view,” “Search for a user,” and“Find open workspace.” As shown, a user of the UE may select the optionto find an open workspace. Based on this selection, and as shown in FIG.1B, a workspace (e.g., the nearest workspace to the UE's currentlocation, such as Flex Space B in this example) navigation instructionsmay be generated and provided to the UE. The navigation instructions mayinclude, for instance, an overlay on the visual representation (shown inthe figure as a series of dots). The navigation instructions mayadditionally, or alternatively, include a list of directions from theUE's current location to the determined workspace. The direction mayinclude annotations that may assist the user of the UE in navigating.For example, the navigation instructions may indicate that a picture ofa kitten will be visible from where the user should make a right turn.The navigation instructions may also indicate other useful instructions,such as a door code needed to enter the workspace. In some embodiments,the navigation instructions (or another part of the GUI) may includesensor readings and/or other types of real-time data (e.g., as receivedfrom one or more Internet of Things (“IoT”) devices or other types ofsuitable devices). The navigation instructions may also indicate anestimated number of steps to complete the navigation route. The numberof steps may be estimated based on, for example, steps taken by otherindividuals (e.g., in the past) to complete the same route or portionsof the same route.

As shown in FIG. 1C, once the UE arrives at the determined workspace,the GUI may prevent an option to display the user's location. In thisexample, assume that the user selects “No.” As shown in FIG. 1D, theuser may be notified that his/her location is private (e.g., “[Yourlocation is private]” in the title bar of the GUI). The GUI may alsoshade the room in which the UE is located differently from the otherrooms. For example, in the figure, Flex Space B may be shaded moredarkly than the occupied rooms.

In FIG. 1D, the user may select the “Search for a user” option. Based onthis selection, the user may be given an opportunity to enter a name ofa user that he/she wishes to locate. In this example, the name “Brian L”has been entered (e.g., via typing, voice input, or some other suitabletechnique). As shown in FIG. 1E, the user “Brian L.” may have beenlocated, and the GUI may indicate that Brian L. is on the same floor asthe UE. In some embodiments, more specific information may be provided(e.g., which room in which Brian L. is located). An option may furtherbe presented to provide directions to the room in which Brian L. islocated, the selection of which may cause navigation instructions (e.g.,similar to those shown in FIG. 1B) to be presented.

Building and presenting a representation of a place, in accordance withembodiments described herein, may allow individuals to clearly determinetheir whereabouts, as well as features of the place in which they may beinterested. As discussed herein, the information about the place may beupdated (e.g., if a new sign is installed, if a room is renovated,etc.), which may avoid confusion that might be caused by the visualrepresentation being different from the actual place. Maintainingup-to-date information about devices or users within the place may allowusers to make informed decisions about what they would like to do orwhere they would like to go in the place (e.g., walk to an availableworkspace and avoid walking to an occupied workspace). The up-to-dateinformation may also be used to assist future users. For example, whilea given path may be the shortest between two given points, someembodiments may recognize that users take a different path, and thatpath may be suggested instead of the shortest path.

FIG. 2 illustrates example environment 200, in which systems and/ormethods described herein may be implemented. As shown in FIG. 2,environment 200 may include UE 205, base station 210, Serving Gateway(“SGW”) 215, Mobility Management Entity (“MME”) 220, PDN gateway (“PGW”)225, Service Capability Exposure Function (“SCEF”) 227, policy andcharging rules function (“PCRF”) 230, home subscriber server(“HSS”)/authentication, authorization, accounting (“AAA”) server 235(hereinafter referred to as “HSS/AAA server 235”), Place AttributeInformation Repository (“PAIR”) 240, user interface system 245, PDN 250,and Real-Time Assistance System (“RTAS”) 255.

While “direct” connections are shown in FIG. 2 between certain devices,some devices may communicate with each other via one or moreintermediary devices (e.g., routers, switch, hubs, etc.) or networks(e.g., an Ethernet backhaul network (“EBH”) and/or some other type ofnetwork). Furthermore, some of the connections shown in FIG. 2 may belogical connections, and may represent the communication betweendifferent logical portions of a single device. Further, in someimplementations, some devices, shown in FIG. 2, may communicate witheach other even though connections are not shown between such devices inthe figure.

Environment 200 may include an evolved packet system (“EPS”) thatincludes a Third Generation Partnership Project (“3GPP”) radio accessnetwork (“RAN”) and/or an Evolved Packet Core (“EPC”) network that isoperated based on a 3GPP wireless communication standard. The RAN maybe, or may include, a Long-Term Evolution (“LTE”) network, a fifthgeneration (“5G”) RAN, etc., that each include one or base stations 210(which may take the form of evolved NodeBs (“eNBs”)), via which UE 205may communicate with the EPC network. The EPC network may include one ormore SGWs 215, PGWs 225, SCEFs 227, and/or MMEs 220, and may enable UE205 to communicate with PDN 250 and/or an Internet protocol (“IP”)multimedia subsystem (“IMS”) core network (not shown). The IMS corenetwork may include and/or communicate with HSS/AAA server 235, and maymanage authentication, session initiation, account information, a userprofile, etc., associated with UE 205.

UE 205 may include a computation and communication device, such as awireless mobile communication device that is capable of communicatingwith base station 210 and/or PDN 250. UE 205 may be, or may include, aradiotelephone; a personal communications system (“PCS”) terminal (e.g.,a device that combines a cellular radiotelephone with data processingand data communications capabilities); a personal digital assistant(“PDA”) (e.g., a device that may include a radiotelephone, a pager,Internet/intranet access, etc.); a smart phone; a laptop computer; atablet computer; a camera; a personal gaming system; an IoT device(e.g., a sensor, a smart home appliance, or the like); a Mobile toMobile (“M2M”) device; or another type of mobile computation andcommunication device. UE 205 may send traffic to and/or receive trafficfrom PDN 250 via base station 210, SGW 215, PGW 225, and/or SCEF 227.

Base station 210 may each include one or more network devices thatreceive, process, and/or transmit traffic, such as calls, audio, video,text, and/or other data, destined for and/or received from UE 205. Inone example, base station 210 may be part of an LTE network, a 5Gnetwork, another advanced network, etc. Base station 210 may receivetraffic, destined for UE 205, from SGW 215, PGW 225, SCEF 227, and/orPDN 250, and may output the traffic to UE 205. Base station 210 may alsoreceive traffic from UE 205, and may output the traffic to its intendeddestination via SGW 215, PGW 225, SCEF 227, and/or PDN 250.

SGW 215 may include one or more network devices that gather, process,search, store, and/or provide information in a manner described herein.SGW 215 may, for example, aggregate traffic received from one or morebase stations 210, and may send the aggregated traffic to PDN 250 viaPGW 225.

MME 220 may include one or more computation and communication devicesthat perform operations to register UE 205 with the EPS, to establishbearer channels associated with a session with UE 205, to hand off UE205 from the EPS to another network, to hand off UE 205 from the othernetwork to the EPS, and/or to perform other operations. MME 220 mayperform policing operations on traffic destined for and/or received fromUE 205. MME 220 may, in some embodiments, receive messages via controlplane signaling, which are destined to and/or sent from UE 205. In someembodiments, MME 220 may control plane signaling for UE 205 from SCEF227, and/or may forward control plane signaling from UE 205 to PDN 250via SCEF 227.

PGW 225 may include one or more network devices that gather, process,search, store, and/or provide information in a manner described herein.PGW 225 may aggregate traffic received from one or more SGWs 215, etc.and may send the aggregated traffic to PDN 250. PGW 225 may also, oralternatively, receive traffic from PDN 250 and may send the traffictoward UE 205 via base station 210 and/or SGW 215.

SCEF 227 may include one or more network devices that gather, process,search, store, and/or provide information in a manner described herein.SCEF 227 may aggregate traffic received from PDN 250 (and/or one or moreother devices and/or systems) and may send the aggregated traffic to UE205 (e.g., via MME 220). SCEF 227 may also, or alternatively, receivetraffic from UE 205 (e.g., via MME 220) and may send the traffic towardPDN 250.

PCRF 230 may include one or more devices that aggregate information toand from the EPC network and/or other sources. PCRF 230 may receiveinformation regarding policies and/or subscriptions from one or moresources, such as subscriber databases and/or from one or more users(such as, for example, an administrator associated with PCRF 230).

HSS/AAA server 235 may include one or more devices that manage, update,and/or store, in a memory associated with HSS/AAA server 235, profileinformation associated with a subscriber. HSS/AAA server 235 may performauthentication, authorization, and/or accounting operations associatedwith the subscriber and/or a communication session with UE 205.

PAIR 240 may include one or more devices that perform functionalitydescribed herein. For example, PAIR 240 may generate a node map based oninformation received from HSS/AAA server 235, UE 205, and/or one or moreother information sources. As described below, the node map may be usedin order to generate visual representations of places, and/or navigationinstructions within places. In some embodiments, PAIR 240 maycommunicate with one or more other devices or systems (e.g., HSS/AAAserver 235, user interface system 245, and/or RTAS 255) via PDN 250and/or via another type of interface. For example, in some embodiments,PAIR 240 may include a proprietary and/or dedicated communicationpathway between PAIR 240 and HSS/AAA server 235 (e.g., a communicationpathway that does not include PDN 250, and/or does not include theInternet).

User interface system 245 may include one or more devices that performfunctionality described herein. For example, user interface system 245may communicate with UE 205 to present information (e.g., graphicalinformation that is derived from information stored and/or provided byPAIR 240) about one or more places. User interface system 245 may, insome embodiments, process feedback from UE 205 (e.g., requests forinformation, feedback regarding navigation instructions, etc.), and maynotify PAIR 240 and/or RTAS 255 regarding the feedback. As describedbelow, node maps and/or other information associated with places may bemodified based on the feedback.

RTAS 255 may include one or more devices that perform functionalitydescribed herein. For example, RTAS 255 may receive and/or otherwisedetermine information associated with UE 205 (e.g., locationinformation, orientation information, or the like). In some embodiments,the information may be received while UE 205 is interacting with userinterface system 245 and/or PAIR 240 (e.g., is in the process ofreceiving or presenting navigation instructions, etc.). In someembodiments, RTAS 255 may communicate with UE 205 to receive theinformation regarding UE 205. In some embodiments, RTAS 255 maycommunicate with one or more other devices or systems (e.g., MME 220,HSS/AAA server 235, etc.) in order to determine information associatedwith UE 205 (e.g., user profile information of a user associated with UE205, network-determined location of UE 205, etc.).

PDN 250 may include one or more wired and/or wireless networks. Forexample, PDN 250 may include an IP-based PDN, a wide area network(“WAN”) such as the Internet, a private enterprise network, and/or oneor more other networks. UE 205 may connect, through PGW 225, to dataservers, application servers, other UEs 205, and/or to other servers orapplications that are coupled to PDN 250. PDN 250 may be connected toone or more other networks, such as a public switched telephone network(“PSTN”), a public land mobile network (“PLMN”), and/or another network.PDN 250 may be connected to one or more devices, such as contentproviders, applications, web servers, and/or other devices, with whichUE 205 may communicate.

FIG. 3 illustrates another example environment 300, in which one or moreembodiments may be implemented. Generally speaking, similar operationsmay be performed in environment 200 as in environment 300, in order tohandle user input in accordance with embodiments described herein.Environment 300 may correspond to a 5G network, and/or may includeelements of a 5G network.

As shown in FIG. 3, environment 300 may include UE 205, RAN 310, AMF315, Session Management Function (“SMF”) 320, Policy Control Function(“PCF”) 325, Application Function (“AF”) 330, User Plane Function(“UPF”) 335, Data Network (“DN”) 355, Authentication Server Function(“AUSF”) 345, Unified Data Management (“UDM”) 350, PAIR 240, userinterface system 245, and/or RTAS 255.

The quantity of devices and/or networks, illustrated in FIG. 3, isprovided for explanatory purposes only. In practice, environment 300 mayinclude additional devices and/or networks; fewer devices and/ornetworks; different devices and/or networks; or differently arrangeddevices and/or networks than illustrated in FIG. 3. For example, whilenot shown, environment 300 may include devices that facilitate or enablecommunication between various components shown in environment 300, suchas routers, modems, gateways, switches, hubs, etc. Alternatively, oradditionally, one or more of the devices of environment 300 may performone or more functions described as being performed by another one ormore of the devices of environments 300. Devices of environment 300 mayinterconnect with each other and/or other devices via wired connections,wireless connections, or a combination of wired and wirelessconnections. In some implementations, one or more devices of environment300 may be physically integrated in, and/or may be physically attachedto, one or more other devices of environment 300.

RAN 310 may be, or may include, a 5G RAN that includes one or more basestations, via which UE 205 may communicate with one or more otherelements of environment 300. UE 205 may communicate with RAN 310 via anair interface. For instance, RAN 310 may receive traffic (e.g., voicecall traffic, data traffic, messaging traffic, signaling traffic, etc.)from UE 305 via the air interface, and may communicate the traffic toUPF 335, and/or one or more other devices or networks. Similarly, RAN310 may receive traffic intended for UE 305 (e.g., from UPF 335, and/orone or more other devices or networks) and may communicate the trafficto UE 305 via the air interface.

AMF 315 may include one or more computation and communication devicesthat perform operations to register UE 305 with the 5G network, toestablish bearer channels associated with a session with UE 305, to handoff UE 305 from the 5G network to another network, to hand off UE 305from the other network to the 5G network, and/or to perform otheroperations. In some embodiments, the 5G network may include multipleAMFs 315, which communicate with each other via the NG14 interface(denoted in FIG. 3 by the line marked “NG14” originating and terminatingat AMF 315).

SMF 320 may include one or more network devices that gather, process,store, and/or provide information in a manner described herein. SMF 320may, for example, facilitate in the establishment of communicationsessions on behalf of UE 305. In some embodiments, the establishment ofcommunications sessions may be performed in accordance with one or morepolicies provided by PCF 325.

PCF 325 may include one or more devices that aggregate information toand from the 5G network and/or other sources. PCF 325 may receiveinformation regarding policies and/or subscriptions from one or moresources, such as subscriber databases and/or from one or more users(such as, for example, an administrator associated with PCF 325).

AF 330 may include one or more devices that receive, store, and/orprovide information that may be used in determining parameters (e.g.,quality of service parameters, charging parameters, or the like) forcertain applications.

UPF 335 may include one or more devices that receive, store, and/orprovide data (e.g., user plane data). For example, UPF 335 may receiveuser plane data (e.g., voice call traffic, data traffic, etc.), destinedfor UE 205, from DN 355, and may forward the user plane data toward UE205 (e.g., via RAN 310, SMF 320, and/or one or more other devices). Insome embodiments, multiple UPFs 335 may be deployed (e.g., in differentgeographical locations), and the delivery of content to UE 305 may becoordinated via the NG9 interface (e.g., as denoted in FIG. 3 by theline marked “NG9” originating and terminating at UPF 335). Similarly,UPF 335 may receive traffic from UE 205 (e.g., via RAN 310, SMF 320,and/or one or more other devices), and may forward the traffic toward DN355. In some embodiments, UPF 335 may communicate (e.g., via the NG4interface) with SMF 320, regarding user plane data processed by UPF 335.As mentioned above, this information may aid SMF 320 in monitoring(e.g., tracking, counting, etc.) the traffic for particular subscribers.

DN 355 may include one or more wired and/or wireless networks. Forexample, DN 355 may include an IP-based PDN, a WAN such as the Internet,a private enterprise network, and/or one or more other networks. UE 205may communicate, through DN 355, with data servers, application servers255, other UEs 205, and/or to other servers or applications that arecoupled to DN 355. DN 355 may be connected to one or more othernetworks, such as a public switched telephone network (“PSTN”), a PLMN,and/or another network. DN 355 may be connected to one or more devices,such as content providers, applications, web servers, and/or otherdevices, with which UE 205 may communicate.

AUSF 345 and UDM 350 may include one or more devices that manage,update, and/or store, in one or more memory devices associated with AUSF345 and/or UDM 350, profile information associated with a subscriber.AUSF 345 and/or UDM 350 may perform authentication, authorization,and/or accounting operations associated with the subscriber and/or acommunication session with UE 305.

As similarly described above with respect to environment 200, PAIR 240may, in some embodiments, be an internal component with respect to oneor more other devices and/or systems discussed with regard toenvironment 300. For example, PAIR 240 may have a dedicated interface(shown as “NG-PAIR”) between PAIR 240 and UDM 350, so that PAIR 240 cancommunicate with UDM 350 without traversing the Internet or DN 355.

FIG. 4 illustrates example data sources that can be used by PAIR 240, inaccordance with some embodiments. For example, PAIR 240 may use a floorplan, augmented reality (“AR”) markers, radio frequency (“RF”)fingerprint information, geographical location information, and/or anode map. The floor plan may be, for example, a schematic or other typeof information that defines a layout and/or physical attributes of aplace. For example, the floor plan may indicate where physical features,such as walls, doors, rooms, sculptures, fixtures, parking spaces,stairs, columns, or other physical objects/features are located. Thefloor plan may be received from, for example, an owner or operator of agiven place (e.g., an owner or operator of a building, parking lot,outdoor venue, etc.). The floor plan may include a diagram or picture,and/or may include a data structure that denotes (e.g., using acoordinate system) where objects and/or features are located. In someembodiments, the floor plan may be a two-dimensional (e.g., overhead)representation of a place. In some embodiments, the floor plan may be athree-dimensional (e.g., orthogonal) representation of a place.

The AR marker information may include features that may be visible tousers in a given place. For example, AR marker information may indicatesigns, posters, or other wall hangings. The AR information may includeinformation that is similar to, or corroborates, floor plan information.For example, the floor plan information may indicate that a door islocated at a certain point in a room, and the AR information may includea picture of the door, as well as an indication of where in the room thedoor is located. In this sense, some of the AR marker information maysupplement some of the floor plan information. The AR information may,in some embodiments, include any visible feature that may be detectedby, for example, a camera of a mobile telephone, a security camera,and/or some other camera. In some embodiments, the AR information may bereceived or generated as part of a dedicated scanning process (e.g., anowner or operator of PAIR 240, and/or some other individual) maypurposely “sweep” a place with a camera, in order to collect images ofsome or all of the place. Additionally, or alternatively, as users arepresent in the place, they may hold devices (e.g., mobile telephones,tablets, etc.) in such a manner that the devices are able to use acamera (e.g., a rear-facing camera and/or a front-facing camera) tocapture images of the place. This image collection may be performedbased on express consent granted by the user (e.g., an “opt-in”), andcollected images may be subject to review by the user and furthersubject to immediate deletion upon the user's request.

Based on the captured images, PAIR 240 may use a suitable imagerecognition technique to identify distinct objects in place. PAIR 240may also use contextual information to determine, or estimate, where inthe place the detected objects are. For example, PAIR 240 may receive animage of two doors, three feet apart. PAIR 240 may analyze the floorplan and determine that the place includes only one instance of twodoors, three feet apart. Based on this analysis, PAIR 240 may identifythat the two doors, identified in the image, are located at thedetermined location in the place. Additionally, or alternatively, PAIR240 may use location information included in the image itself (e.g.,Exchangeable Image File Format (“EXIF”) and/or other type of metadatainformation), and/or location information provided in conjunction withthe image (e.g., where the location is determined by UE 205, asdiscussed below) to determine where the AR markers are located in theplace.

The RF fingerprint information may include information that indicates RFsignals detected in the place. For example, the RF fingerprintinformation may indicate types of RF signals detected (e.g., WiFisignals, BLE signals, and/or other types of RF signals) in the place(e.g., by UEs 205 present in the place). The RF fingerprint informationmay also include supplemental information, such as timestampinformation, signal strength information, interference information, etc.The timestamp information may be useful in determining factors that canaffect the determination of the source of RF signals. For example, atone time, the received power of WiFi signals from a particular WiFiaccess point may be relatively weak due to a large quantity of UEsaccessing the WiFi access point, while the received power of WiFisignals from the same WiFi access point may be relatively strong atanother time when fewer 205 are accessing the WiFi access point. Basedon the RF fingerprint information received over time from one or moreUEs 205, PAIR 240 may determine or estimate the location of RF-emittingdevices. In some embodiments, the RF fingerprint information may includemanually-provided information regarding RF-emitting devices, such as thephysical location of the RF-emitting devices, SSIDs and/or passwordsthat can be used to access WiFi access points, names of BLE beacons,etc.

In some embodiments, the RF fingerprint may include geofencinginformation, and/or information that may be used for geofencing (e.g.,in conjunction with floor plan information). For example, the RFfingerprint may indicate locations, RF types (e.g., WiFi, Bluetooth,etc.), hardware/device identifiers, and/or other types of informationthat can indicate where geofencing devices are located. For instance,each room on a floor may have a geofencing device (e.g., a BLE beacon)placed in a doorway of the room, and the RF information may includeinformation identifying each BLE device (e.g., using a hardwareidentifier, such as a MAC address and/or an identifier broadcasted bythe BLE device) as being associated with a particular room (e.g., usinga room number and/or some other type of indicator of location within theplace).

The geographical information, used by PAIR 240, may include ageographical region that bounds, defines, or otherwise describes theplace. For example, the geographical information may include a set oflatitude and longitude coordinates (e.g., four coordinate pairs for arectangle-shaped place, six coordinate pairs for a hexagonally shapedplace, and so on), a physical address (e.g., “221B Baker Street”), acoordinate point and a radius (e.g., a circle where the center is thecoordinate point), and/or some other way of representing a physicallocation. The geographical information may be provided by an owner oroperator of PAIR 240 or a given place, and/or may be collected (e.g.,subject to express user consent, review, and deletion, as discussedabove) by a UE of a user that is present in the place.

The node map may represent attributes or features of the place as nodes.For example, one room may be represented by a first node in the nodemap, another room may be represented by a second node in the node map,an arbitrary point in the place may be represented by a third node inthe node map, a picture hanging on a wall may be represented by a fourthnode in the node map, and so on. Generally speaking, the node map mayindicate interactions of users between various features or attributes ofa place. The nodes in the node map may, in some embodiments, eachrepresent a physical location or a region (e.g., a 1-meter wide circle,a 0.5×0.5-meter square, etc.). The node map may include connectionsbetween nodes, which may indicate the likelihood of a user physicallymoving from one node to another.

A simplified example of a node map 500 is shown in FIG. 5A. As shown,node map 500 may include nodes A-D. Node map 500 also includes a seriesof 1-way connections between nodes, represented as unidirectionalarrows. These arrows may represent the likelihood of a user moving fromone node (e.g., a location represented by a node) to another node (e.g.,a location represented by the other node). For example, for a usercurrently at Node A, the node map may indicate that the user'slikelihood of moving Node B is 30%, to Node C is 20%, and to Node D is50%.

In some embodiments, the information stored in node map 500 (e.g., theidentification of the nodes) may be based on an analysis of other typesof information received by PAIR 240. For instance, PAIR 240 may analyzea floor plan, and may automatically (e.g., using image recognitiontechniques, pattern recognition techniques, and/or using some othersuitable technique) identify attributes or features that should beassociated with a node. For instance, PAIR 240 may be configured togenerate a node when a door is detected in the floor plan, and/or whenAR information indicates that a door is present. As another example,PAIR 240 may be configured to generate a node when a corner of a walkwayis detected (e.g., based on floor plan information and/or ARinformation). As yet another example, PAIR 240 may be configured togenerate a node, and/or otherwise store information, when detectinghandicap access features in the place (e.g., a ramp, a handicap sign, anautomatic door, a bathroom stall that is larger than surroundingbathroom stalls, or the like). In some embodiments, PAIR 240 may furtheridentify boundaries associated with the nodes, where boundaries can beused to indicate whether a given UE 205 is in, near, at, is in a viewingfrustum of, etc., a given attribute or feature of a place. For example,a door may have a relatively small boundary (e.g., within 0.5 meter ofthe threshold of the door), while a wall hanging may have a relativelylarge boundary (e.g., a bounded region that represents areas from wherethe wall hanging is visible). In some embodiments, the boundaries of oneor more nodes may be manually specified or modified.

The information stored in node map 500 (e.g., the likelihood of movementfrom one node to another) may be based on information received from UEs205 (e.g., based on real-time feedback from UEs 205, such as locationinformation, orientation information video capture information, and/orother information discussed below with respect to FIG. 6—subject toexplicit user consent, review, and deletion).

In some embodiments, node map 500 may include a temporal element. Forinstance, different concurrent versions of node map 500 may indicatelikely user movements within different thresholds of time. For instance,one version of node map 500 may indicate likely user movements within 30seconds of arriving at a given node, while another version of node map500 may indicate likely user movements within 10 minutes of arriving ata given node.

For instance, as shown, node map 500 shows an arrow from Node B to NodeB, and an arrow from Node D to Node D. These arrows may indicate thelikelihood that a user will stay at Node B or Node D, respectively,within a given time threshold. Assume, for example, that the timethreshold associated with FIG. 5A is 10 minutes. Continuing with theexample of FIG. 5A, this means that 90% users who arrived at Node Bstayed at Node B for 10 minutes or longer, while 0% of users went fromNode B to Nodes A or C within 10 minutes, and 10% of users went fromNode B to Node D within 10 minutes. Different versions of node map 500may be used for different purposes. For example, a relatively short(e.g., 5 seconds) time threshold may be used for users who wish tonavigate from one node to another, while a relatively long (e.g., 1hour) time threshold may be used for users who wish to find a locationto stay for a relatively long time (e.g., an office workspace).

In some embodiments, while not shown, node map 500 may includeadditional information. For example, node map 500 may includeinformation indicating the physical distance between nodes, historicalinformation relating to how long users took to travel from one node toanother (e.g., expressed in terms of steps taken and/or time, which maybe an average, a median, a minimum, a maximum, and/or some othermathematical or statistical function). In some embodiments, a distinctnode map may be generated for each place. In some embodiments, a givenplace may be associated with multiple node maps.

FIG. 5B illustrates another example representation of node map 500. Asshown, node map 500 may be represented as table 550. Table 550, shownhere, includes the same information as node map 500. For example, table550 reflects that the likelihood of a user moving from Node A to Node Bis 30%, from Node A to Node C is 20%, and so on.

As discussed above, multiple node maps, or multiple versions of nodemaps, may be associated with the same place. For example, different nodemaps may be used for different individual users (e.g., based on themovements and/or other information associated with individual users), ordifferent types of users (e.g., where “types” of user may be delineatedby demographics and/or other categories or differentiatingcharacteristics). For instance, one node map may be used for handicappedindividuals, while another node map may be used for non-handicappedindividuals. The node map for handicapped individuals may, in somescenarios, be different because handicapped individuals may preferdifferent paths (e.g., paths with ramps and/or other handicap accesscharacteristics).

In some embodiments, a distinct node map may be generated for a givenpair of starting and ending nodes. For example, assuming that a userdesires to go from a location associated with Node A to a locationassociated with Node B. A particular node map may reflect a probablepath (e.g., a set of nodes) that the user would take from Node A to NodeB (e.g., based on previous users' or devices' behavior with respect totraveling from Node A to Node B). As discussed below, node maps may beupdated and/or refined on an ongoing basis, in order to enhance users'experiences.

FIG. 6 illustrates example information sources that can be used by RTAS255 to perform one or more operations described herein. For example,RTAS 255 may receive information from UE 205, such as orientationinformation, pedometer information, video capture information, locationinformation, user input, and/or other types of information. In someembodiments, RTAS 255 may receive the information from UE 205 while UE205 is in the process of navigating from one point in a place (e.g.,node) to another. In some embodiments, RTAS 255 may receive theinformation from UE 205 on an ongoing basis (e.g., periodically orintermittently—where the collection and storage of any and all suchinformation is subject to express user consent, review, and deletion, asdiscussed above). As discussed below, the information, received by RTAS255 from UE 205, may be generated by UE 205 and/or may be based oninformation received by UE 205. The various types of informationprovided by UE 205 may be provided with timestamp information, so thatRTAS 255 is able to determine the time(s) that correspond to the variousreceived information.

The orientation information may indicate a direction that UE 205 isfacing. The orientation may be expressed in terms of local space (e.g.,degrees of rotation on X-, Y-, and Z-axes) and/or in terms of magneticdeclination (e.g., degrees from North). In some embodiments, theorientation information may be determined by UE 205 (e.g., using amagnetometer, accelerometer, and/or other device or component that issuitable to determine the orientation of UE 205). In some embodiments,UE 205 may determine the orientation information with the assistance ofone or more external devices, such as a wearable device (e.g., “smart”watch, “smart” glasses, “smart” jewelry, etc.).

The pedometer information may indicate a quantity of steps taken by auser of UE 205 (e.g., a user that is carrying UE 205, and/or isotherwise physically holding or attached to UE 205). In someembodiments, the pedometer information may be determined by UE 205(e.g., using any suitable component or collection of components of UE205). In some embodiments, the orientation information may be determinedby UE 205 with the assistance of, and/or may be received from, one ormore other devices (e.g., a wearable “smart” device that counts stepstaken and/or otherwise includes pedometer functionality).

The video capture information may include images or video captured by animage capture device (e.g., camera) of UE 205. For example, a user maycarry UE 205 in such a manner that a front-facing and/or rear-facingcamera is able to capture images and/or video. As another example, UE205 may be communicatively coupled to a wearable device (e.g., a bodycamera and/or some other wearable device with video capturefunctionality) that can capture video. As similarly noted above, thecaptured video may be subject to express user consent, review, anddeletion.

The location information may indicate a location (e.g., a geographicallocation) of UE 205. The location information may be two-dimensional(e.g., latitude and longitude coordinates, and/or coordinates on a localsystem (e.g., X- and Y-coordinates with a reference point that is withina given place)) or three-dimensional (e.g., where height is expressed interms of altitude, elevation above a given reference point, the floor ofa building, and/or some other suitable way of expressing height). Thelocation information may be determined by UE 205 (e.g., using a GlobalPositioning System (“GPS”) component and/or using some other suitabletechnique) and/or may be determined by UE 205 with the assistance of, ormay be received from, one or more other devices or systems (e.g., from awireless telecommunications network that uses triangulation techniquesto determine the location of UE 205, a geofencing system, or the like).

The user input information may include information manually provided bya user of UE 205. For example, UE 205 may provide prompts, such as “Rateyour navigation experience from 1-5 stars,” to which a user may providefeedback. As another example, the user input information may includeinteractions with UE 205 relating to modifying a route between nodes(e.g., a user may be dissatisfied with a route and may re-input the samedestination in hopes of being provided with a different route). As yetanother example, the user input information may include information thatimplies that a user was satisfied with a route (e.g., no furtherrequests for navigation instructions were requested by the user within athreshold time of previous navigation instructions being completed).

As mentioned above, a given UE 205 may be, or may include, an IoT devicewith one more sensors (e.g., sensors that collect the same, additional,and/or different types of data than the examples given above). Forinstance, a particular IoT device may include a temperature sensor, anoccupancy or motion sensor, a light sensor, a barometric sensor, ahumidity sensor, and/or some other type of sensor. The data sensed by anIoT device may also be provided to RTAS 255 and/or PAIR 240, in order toassist with navigation instructions and/or with displaying a visualrepresentation of a place. For instance, if one route (e.g., a pathwaybetween one or more nodes) is hotter than usual (e.g., where an IoTdevice that includes a temperature sensor has reported a temperaturethat is above a threshold temperature), navigation instructions thatinclude that route may be modified to either remove that route, providea notification to a user that the route includes a potentiallyuncomfortable temperature, and/or some other corrective action inresponse to detecting the high temperature.

As another example, in addition to (or in lieu of) modifying navigationinstructions, the information received from IoT devices may be presentedvia a GUI (e.g., similar to the example GUI shown in FIGS. 1A-1E). Forinstance, when a graphical representation of a particular place ispresented, information from IoT devices may also be presented.Furthermore, the information from IoT devices may be overlaid at, ornear (e.g., within a threshold distance of), a location in the visualrepresentation that corresponds to where the IoT devices are physicallylocated. For example, if a temperature sensor is physically located nextdo a particular corner in a place, the visual representation of theplace may include an overlay of a numerical value, that indicates themeasured temperate (e.g., in real-time or near-real-time in theparticular corner).

FIG. 7 illustrates example interactions between PAIR 240 (discussedabove with reference to FIGS. 4-5B) and RTAS 255 (discussed above withreference to FIG. 6) and other devices (i.e., user interface system 245and UE 205, in this example). One-way arrows are shown in this figure toshow examples of which devices may communicate information to whichother devices. However, the directionality of these arrows is not meantto suggest that communication could not occur in the opposite direction.For example, one device may request information from another device, butthe requests are not illustrated in the figure for the sake of brevityand clarity.

PAIR 240 may, for example, store information regarding one or moreplaces, as discussed above. The information stored by PAIR 240, in someembodiments, may include one or more node maps associated with one ormore places. As discussed above, the information stored by PAIR 240 maybe based on manually provided information, information received from UEs205, and/or information from another source.

UE 205 may execute an application that is configured to communicatewith, and/or may otherwise (e.g., via by visiting a Uniform ResourceLocator (“URL”) in a web browser) communicate with, user interfacesystem 245 to obtain information regarding a given place (e.g., a placein which UE 205 is presently located, or a place in which a user of UE205 is otherwise interested). User interface system 245 may receive thelocation of UE 205 from UE 205 itself (e.g., when UE 205 requests theinformation from user interface system 245, UE 205 may include thelocation of UE 205), from RTAS 255, and/or from some other source. Userinterface system 245 may identify one or more places that correspond tothe request (e.g., a place whose physical location matches, or is withina threshold distance of, the location of UE 205 or a location indicatedby a user of UE 205 as being of interest to the user).

Once user interface system 245 has determined the requested place (orplaces), user interface system 245 may obtain information regarding theplace from PAIR 240. For example, user interface system 245 may obtain anode map, a graphical layout of the place, and/or other information fromPAIR 240. User interface system 245 may generate a visual representationof the place based on the received information. For example, thereceived information may include a visual floor plan, as well asinformation that indicates additional features and the types andlocations of the features (e.g., information indicating an office, adoor, a statue, a sculpture, a wall hanging, or the like). PAIR 240 mayalso provide additional information associated with the features (e.g.,a door code for a door, a WiFi SSID for a WiFi access point, or thelike). In some embodiments, the node map may include the informationregarding some or all the features of the place. User interface system245 may use the visual floor plan in conjunction with the additionalinformation regarding the features of the place to generate the visualrepresentation of the place, for presentation by UE 205 via a GUI.

The GUI may include selectable options similar to those shown in FIGS.1A-1E. For example, the GUI may include buttons relating to navigation,searching for users, selecting another place to view, etc. Specificfeatures may also include selectable options. For example, referringagain to FIG. 1A, the SSID of the WiFi access point (i.e., “WiFi1” inthis example) may be displayed when a user of UE 205 selects (e.g.,clicks, uses a stylus, touches a touchscreen, etc.) the icon of the WiFiaccess point. As another example, selecting an available workspace maycause UE 205 to present navigation instructions from the currentlocation of UE 205 to the selected workspace.

The available interactions may be defined by the types of the features(e.g., features that are of the type “WiFi access point” may beassociated with a selectable option to display the SSID, features thatare of the type “flex space” may be associated with a selectable optionto navigate to the flex space, and so on). As discussed above, the typeof a feature may be automatically determined by using image recognition,pattern recognition, and/or other techniques. The potential selectableoptions (e.g., select to view SSID), as well as other associatedinformation (e.g., the SSID itself) may be stored by PAIR 240 as part ofthe information associated with the place (e.g., may be stored in thenode map).

When presented by UE 205, user interface system 245 may process inputsand/or other interactions via the GUI. For example, referring again toFIG. 1A, when the “Find open workspace” button is selected, UE 205 maynotify user interface system 245 of the selection. Based on theselection, user interface system 245 may identify a relevant node map.In one example, user interface system 245 may identify one or moreattributes associated with UE 205 (e.g., may receive the attributes fromUE 205 or from RTAS 255), such as demographics information and/or otherdifferentiating information based on which different node maps have beengenerated. The one or more attributes may be compared to attributesassociated with the node maps (e.g., if UE 205 is associated with ahandicapped user, a node map associated with handicapped users may beidentified). In some embodiments, user interface system 245 may receiveall node maps associated with the place, and may select the relevantnode map(s). In some embodiments, PAIR 240 may select the relevant nodemap(s) (e.g., based on receiving information relevant to selecting thenode map(s) from UE 205, user interface system 245, and/or RTAS 255).

User interface system 245 may use the node map to generate navigationinstructions. For example, as discussed above, the node map may includethe likelihood that UE 205 would traverse a certain path between nodes,and/or travel from one node do another, and user interface system 245may generate the navigation instructions using these likelihoods. Insome embodiments, the navigation instructions may include annotations orother information, based on attributes of nodes. For example, if one ofthe nodes is associated with a wall hanging, the node map may includeinformation indicating content of the wall hanging (or other visiblyidentifiable attributes of the wall hanging), and the navigationinstructions may include some or all of the information associated withthe wall hanging. User interface system 245 may proceed to provide thenavigation instructions to UE 205, which may present the instructions ina GUI (e.g., as similarly shown in FIG. 1B). User interface system 245may also notify PAIR 240 that navigation instructions were provided toUE 205, so that PAIR 240 can refine the node map based on how the UE 205behaves after the navigation instructions are provided.

For example, UE 205 may communicate, in real-time or near-real-time,with RTAS 255 to provide information regarding UE 205 while navigationinstructions are presented via UE 205. For instance, UE 205 mayperiodically or intermittently (e.g., every 5 seconds, every 30 seconds,every time a new navigation instruction is presented, etc.) providestatus information to RTAS 255, such as location information,orientation information, video capture information, or the like.Additionally, or alternatively, UE 205 may receive user feedback (e.g.,a selection indicating that a new route is desired, a rating of thenavigation instructions, etc.).

RTAS 255 may provide some or all of the information, received from UE205, to PAIR 240 and/or user interface system 245. PAIR 240 may, in someembodiments, refine the node map, and/or other information associatedwith the place, based on the information received from UE 205. In someembodiments, PAIR 240 may use machine learning, neural networks,artificial intelligence (“AI”), and/or other techniques to automaticallyrefine the node map and/or information associated with the place. Insome embodiments, PAIR 240 may refine a node map by adding nodes thatwere not previously present, or by removing nodes that were previouslypresent. For example, if a new fixture is installed in a place, videoinformation from one or more UEs 205 may reveal that the fixture hasbeen installed, and PAIR 240 may add a node associated with the fixture.

In some embodiments, user interface system 245 may use the information,received from UE 205, to present different information via UE 205. Forexample, if user interface system 245 receives information indicatingthat UE 205 has moved from one place to another, user interface system245 may automatically retrieve (e.g., from PAIR 240) one or more nodemaps associated with the new place. As another example, after UE 205 hascompleted a set of navigation instructions, user interface system 245may request feedback on the quality of the instructions, and may passthe feedback to PAIR 240 to enable PAIR 240 to refine the node map(s)associated with the place. As mentioned above, different node maps maybe associated with different attributes of users. When refining the nodemaps, PAIR 240 may, in some embodiments, only refine node maps with thesame attributes of a user of UE 205. In some embodiments, PAIR 240 mayobtain user information (e.g., demographics information, a telephonenumber, an address, user name, etc.) from a user profile repository,such as a device of a wireless telecommunications network (e.g., HSS/AAAserver 235, UDM 350, and/or some other repository that storesinformation regarding users and/or UEs 205), in order to identifyattributes of the user of UE 205.

FIG. 8 illustrates an example process 800 for obtaining and presentinginformation associated with a particular place. In some embodiments,process 800 may be performed by PAIR 240. In some embodiments, some orall of process 800 may be performed by one or more devices in additionto, or in lieu of, PAIR 240 (e.g., user interface system 245 and/or oneor more other devices described herein).

As shown, process 800 may include receiving (at 805) attributeinformation associated with a place, including historical informationassociated with UE activity at the place. For example, as describedabove (e.g., with respect to FIGS. 4 and 7), PAIR 240 may receivevarious types of information that can be useful in generating a node mapand/or other data structure that represents the place. The informationmay include, for example, floor plan information, RF fingerprintinformation, geographical location information, and/or other types ofinformation. PAIR 240 may, additionally, or alternatively, receiveinformation from RTAS 255, which may include historical information fromone or more UEs 205 (e.g., UEs 205 that have been physically present in,or within a threshold distance of, the place).

Process 800 may further include generating and/or modifying (at 810) anode map, for the place, based on the received attributes and/orhistorical information. For example, as discussed above (e.g., withrespect to FIGS. 4 and 7), PAIR 240 may generate a node map for theplace (e.g., if a node map has not already been generated for theplace). In some embodiments, PAIR 240 may modify a node map associatedwith the place. As also discussed above, multiple node maps (or versionsof the same node map) may be present (e.g., node maps that areassociated with different time thresholds, different user types, etc.).

Process 800 may additionally include generating and/or modifying (at815) a visual representation of the place. For example, PAIR 240 (and/oruser interface system 245) may generate a visual representation byoverlaying icons and/or other graphical elements on a floor plan of theplace. The icons may each represent features of the place (e.g., oneicon may represent a room, another icon may represent a door, anothericon may represent a WiFi access point, and so on). In some embodiments,the visual representation may be generated each time the node map isgenerated and/or modified. In some embodiments, the visualrepresentation may be generated when UE 205 requests the visualrepresentation.

Process 800 may also include presenting (at 820) the visualrepresentation of the place to a particular UE 205. For example, thevisual representation may be provided to UE 205 based on a request fromUE 205 (e.g., a request to view the place, a request to navigate toand/or from the place, etc.).

In some embodiments, the visual representation may be provided to UE 205automatically (e.g., “pushed,” without a request for the visualrepresentation from UE 205). For example, PAIR 240 and/or user interfacesystem 245 may determine (e.g., based on information received from RTAS255 and/or some other source) that UE 205 is located within, or within athreshold distance of, the place. Additionally, or alternatively, PAIR240 may determine that UE 205 is traveling towards the place (e.g.,based on a current location, trajectory, and/or velocity of UE 205), andmay automatically provide the visual representation of the place to UE205 based on the determination that UE 205 is traveling towards theplace. When receiving the visual representation automatically, UE 205may, in some embodiments, cache the visual representation (e.g., storethe visual representation without notifying a user of UE 205 that thevisual representation has been received). The cached visualrepresentation may be displayed on a display device of UE 205 when auser of UE 205 selects an option to view the visual representation.Since the visual representation is already cached, it may be presentedto the user more quickly than if it had needed to be retrieved after theuser requested to view it.

FIG. 9 illustrates an example process 900 for assisting a user innavigating a place based on the node map and further based on real-timefeedback from the user (e.g., from a UE of the user), in accordance withsome embodiments. In some embodiments, process 900 may be performed byuser interface system 245. In some embodiments, one or more otherdevices, in addition to or in lieu of user interface system 245, mayperform some or all of process 900.

As shown, process 900 may include receiving (at 905) a navigationrequest. For example, user interface system 245 may receive a requestfrom UE 205 to navigate from one point (e.g., a first point in a place)to another point (e.g., a second point in the place).

Process 900 may further include identifying (at 910) a starting node, anending node, and a preferred path. For example, user interface system245 may identify a nearest node, in the node map (e.g., a node mapassociated with the place, which may further be a node map that isassociated with one or more attributes of a user of UE 205, such asdemographics attributes), to a current location of UE 205. Userinterface system 245 may also identify a nearest node, in the node map,to the ending point of the navigation request. User interface system 245may determine a path between the starting and ending nodes based on thenode map. For example, user interface system 245 may analyze thelikelihood of movement from each node to another node, and generate apath based on the analysis.

Process 900 may additionally include presenting (at 915) navigationinstructions based on the identified nodes and path. For example, userinterface system 245 may provide instructions, based on the pathidentified at 910, to UE 205. In some embodiments, the instructions mayinclude annotations that are associated with one or more of the nodes inthe path. For instance, as discussed above, one node may be associatedwith a door that has a keycode, and the instructions may include anannotation that includes the keycode.

Process 900 may also include receiving (at 920) updated UE informationduring the navigation. For example, RTAS 255 may receive information,associated with UE 205, after the navigation instructions have beenprovided to UE 205. The information may include, for example, locationinformation, orientation information, etc. (e.g., as discussed abovewith respect to FIGS. 5 and 7).

Process 900 may further include refining (at 920) the node map based onthe received information. For example, as discussed above, the node mapmay be refined based on factors such as whether the navigationinstructions were followed (or a quantity or percentage of instructionsthat were followed, versus how many were not followed), whether thenavigation was completed, whether new navigation instructions wererequested, etc.

FIG. 10 illustrates example components of device 1000. One or more ofthe devices described above may include one or more devices 1000. Device1000 may include bus 1010, processor 1020, memory 1030, input component1040, output component 1050, and communication interface 1060. Inanother implementation, device 1000 may include additional, fewer,different, or differently arranged components.

Bus 1010 may include one or more communication paths that permitcommunication among the components of device 1000. Processor 1020 mayinclude a processor, microprocessor, or processing logic that mayinterpret and execute instructions. Memory 1030 may include any type ofdynamic storage device that may store information and instructions forexecution by processor 1020, and/or any type of non-volatile storagedevice that may store information for use by processor 1020.

Input component 1040 may include a mechanism that permits an operator toinput information to device 1000, such as a keyboard, a keypad, abutton, a switch, etc. Output component 1050 may include a mechanismthat outputs information to the operator, such as a display, a speaker,one or more light emitting diodes (“LEDs”), etc.

Communication interface 1060 may include any transceiver-like mechanismthat enables device 1000 to communicate with other devices and/orsystems. For example, communication interface 1060 may include anEthernet interface, an optical interface, a coaxial interface, or thelike. Communication interface 1060 may include a wireless communicationdevice, such as an infrared (“IR”) receiver, a Bluetooth® radio, or thelike. The wireless communication device may be coupled to an externaldevice, such as a remote control, a wireless keyboard, a mobiletelephone, etc. In some embodiments, device 1000 may include more thanone communication interface 1060. For instance, device 1000 may includean optical interface and an Ethernet interface.

Device 1000 may perform certain operations relating to one or moreprocesses described above. Device 1000 may perform these operations inresponse to processor 1020 executing software instructions stored in acomputer-readable medium, such as memory 1030. A computer-readablemedium may be defined as a non-transitory memory device. A memory devicemay include space within a single physical memory device or spreadacross multiple physical memory devices. The software instructions maybe read into memory 1030 from another computer-readable medium or fromanother device. The software instructions stored in memory 1030 maycause processor 1020 to perform processes described herein.Alternatively, hardwired circuitry may be used in place of or incombination with software instructions to implement processes describedherein. Thus, implementations described herein are not limited to anyspecific combination of hardware circuitry and software.

The foregoing description of implementations provides illustration anddescription, but is not intended to be exhaustive or to limit thepossible implementations to the precise form disclosed. Modificationsand variations are possible in light of the above disclosure or may beacquired from practice of the implementations.

For example, while series of blocks and/or signals have been describedwith regard to FIGS. 7-9, the order of the blocks and/or signals may bemodified in other implementations. Further, non-dependent blocks and/orsignals may be performed in parallel. Additionally, while the figureshave been described in the context of particular devices performingparticular acts, in practice, one or more other devices may perform someor all of these acts in lieu of, or in addition to, the above-mentioneddevices.

The actual software code or specialized control hardware used toimplement an embodiment is not limiting of the embodiment. Thus, theoperation and behavior of the embodiment has been described withoutreference to the specific software code, it being understood thatsoftware and control hardware may be designed based on the descriptionherein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of the possible implementations. Infact, many of these features may be combined in ways not specificallyrecited in the claims and/or disclosed in the specification. Althougheach dependent claim listed below may directly depend on only one otherclaim, the disclosure of the possible implementations includes eachdependent claim in combination with every other claim in the claim set.

Further, while certain connections or devices are shown, in practice,additional, fewer, or different, connections or devices may be used.Furthermore, while various devices and networks are shown separately, inpractice, the functionality of multiple devices may be performed by asingle device, or the functionality of one device may be performed bymultiple devices. Further, multiple ones of the illustrated networks maybe included in a single network, or a particular network may includemultiple networks. Further, while some devices are shown ascommunicating with a network, some such devices may be incorporated, inwhole or in part, as a part of the network.

Some implementations are described herein in conjunction withthresholds. To the extent that the term “greater than” (or similarterms) is used herein to describe a relationship of a value to athreshold, it is to be understood that the term “greater than or equalto” (or similar terms) could be similarly contemplated, even if notexplicitly stated. Similarly, to the extent that the term “less than”(or similar terms) is used herein to describe a relationship of a valueto a threshold, it is to be understood that the term “less than or equalto” (or similar terms) could be similarly contemplated, even if notexplicitly stated. Further, the term “satisfying,” when used in relationto a threshold, may refer to “being greater than a threshold,” “beinggreater than or equal to a threshold,” “being less than a threshold,”“being less than or equal to a threshold,” or other similar terms,depending on the appropriate context.

To the extent the aforementioned implementations collect, store, oremploy personal information provided by individuals, it should beunderstood that such information shall be collected, stored, and used inaccordance with all applicable laws concerning protection of personalinformation. Additionally, the collection, storage, and use of suchinformation may be subject to consent of the individual to such activity(for example, through “opt-in” or “opt-out” processes, as may beappropriate for the situation and type of information). Storage and useof personal information may be in an appropriately secure mannerreflective of the type of information, for example, through variousencryption and anonymization techniques for particularly sensitiveinformation.

No element, act, or instruction used in the present application shouldbe construed as critical or essential unless explicitly described assuch. An instance of the use of the term “and,” as used herein, does notnecessarily preclude the interpretation that the phrase “and/or” wasintended in that instance. Similarly, an instance of the use of the term“or,” as used herein, does not necessarily preclude the interpretationthat the phrase “and/or” was intended in that instance. Also, as usedherein, the article “a” is intended to include one or more items, andmay be used interchangeably with the phrase “one or more.” Where onlyone item is intended, the terms “one,” “single,” “only,” or similarlanguage is used. Further, the phrase “based on” is intended to mean“based, at least in part, on” unless explicitly stated otherwise.

What is claimed is:
 1. A device, comprising: a non-transitorycomputer-readable medium storing a set of processor-executableinstructions; and one or more processors configured to execute the setof processor-executable instructions, wherein executing the set ofprocessor-executable instructions causes the one or more processors to:receive a node map associated with a particular area, wherein the nodemap includes a plurality of nodes that are each associated with arespective location within the particular area; determine, between eachnode in the node map and at least one other node in the node map, alikelihood that a particular user device, that is located in a locationthat is associated with the each node, will move to a location that isassociated with the at least one other node; receive a request tonavigate the particular user device from a first location, in theparticular area, to a second location in the particular area; generate,based on the request and the determined likelihoods, navigationinstructions from the first location to the second location; and outputthe generated navigation instructions.
 2. The device of claim 1, whereinthe likelihood, that the particular user device will move from a firstnode to a second node, of the plurality of nodes, is based on historicalinformation associated with the particular user device.
 3. The device ofclaim 1, wherein the likelihood, that the particular user device willmove from a first node to a second node, of the plurality of nodes, isbased on historical information associated with one or more other userdevices.
 4. The device of claim 1, wherein executing theprocessor-executable instructions further causes the one or moreprocessors to: generate a visual representation of the particular area,the visual representation including a graphical icon for each node, ofthe plurality of nodes; receive information indicating that theparticular user device is located within a threshold distance of aboundary of the particular area, and output, based on the informationindicating that the particular user device is located within thethreshold distance of the boundary of the particular area, the visualrepresentation of the particular area to the particular user device. 5.The device of claim 1, wherein executing the processor-executableinstructions further causes the one or more processors to: generate avisual representation of the particular area, the visual representationincluding a selectable graphical icon for at least one node, of theplurality of nodes; output the visual representation of the particulararea to the particular user device; and receive a selection, from theparticular user device, of a particular selectable graphical iconassociated with a particular node, wherein the second location,indicated in the request, is associated with the selected particularnode.
 6. The device of claim 1, wherein the second location isassociated with a particular room in the particular area, whereinexecuting the processor-executable instructions further causes the oneor more processors to: determine that the navigation instructions havebeen completed; compare a route taken, during the navigation, to thenavigation instructions; determine that the route taken was differentfrom the navigation instructions; and modify at least one of thelikelihoods, between at least two of the nodes in the node map, based onthe route taken being different from the navigation instructions.
 7. Thedevice of claim 1, wherein executing the processor-executableinstructions further causes the one or more processors to: generate aplurality of node maps associated with the particular area, that eachinclude the same nodes, for a plurality of different user devices,wherein the respective likelihoods of traveling from a first node to asecond node, of the plurality of nodes, are different for each one ofthe plurality of node maps.
 8. A non-transitory computer-readable mediumstoring a set of processor-executable instructions, which, when executedby one or more processors, cause the one or more processors to: receivea node map associated with a particular area, wherein the node mapincludes a plurality of nodes that are each associated with a respectivelocation within the particular area; determine, between each node in thenode map and at least one other node in the node map, a likelihood thata particular user device, that is located in a location that isassociated with the each node, will move to a location that isassociated with the at least one other node; receive a request tonavigate the particular user device from a first location, in theparticular area, to a second location in the particular area; generate,based on the request and the determined likelihoods, navigationinstructions from the first location to the second location; and outputthe generated navigation instructions.
 9. The non-transitorycomputer-readable medium of claim 8, wherein the likelihood, that theparticular user device will move from a first node to a second node, ofthe plurality of nodes, is based on historical information associatedwith the particular user device.
 10. The non-transitorycomputer-readable medium of claim 8, wherein the likelihood, that theparticular user device will move from a first node to a second node, ofthe plurality of nodes, is based on historical information associatedwith one or more other user devices.
 11. The non-transitorycomputer-readable medium of claim 8, wherein execution of set ofprocessor-executable instructions further causes the one or moreprocessors to: generate a visual representation of the particular area,the visual representation including a graphical icon for each node, ofthe plurality of nodes; receive information indicating that theparticular user device is located within a threshold distance of aboundary of the particular area, and output, based on the informationindicating that the particular user device is located within thethreshold distance of the boundary of the particular area, the visualrepresentation of the particular area to the particular user device. 12.The non-transitory computer-readable medium of claim 8, whereinexecution of set of processor-executable instructions further causes theone or more processors to: generate a visual representation of theparticular area, the visual representation including a selectablegraphical icon for at least one node, of the plurality of nodes; outputthe visual representation of the particular area to the particular userdevice; and receive a selection, from the particular user device, of aparticular selectable graphical icon associated with a particular node,wherein the second location, indicated in the request, is associatedwith the selected particular node.
 13. The non-transitorycomputer-readable medium of claim 8, wherein the second location isassociated with a particular room in the particular area, whereinexecution of set of processor-executable instructions further causes theone or more processors to: determine that the navigation instructionshave been completed; compare a route taken, during the navigation, tothe navigation instructions; determine that the route taken wasdifferent from the navigation instructions; and modify at least one ofthe likelihoods, between at least two of the nodes in the node map,based on the route taken being different from the navigationinstructions.
 14. The non-transitory computer-readable medium of claim8, wherein execution of set of processor-executable instructions furthercauses the one or more processors to: generate a plurality of node mapsassociated with the particular area, that each include the same nodes,for a plurality of different user devices, wherein the respectivelikelihoods of traveling from a first node to a second node, of theplurality of nodes, are different for each one of the plurality of nodemaps.
 15. A method, comprising: receiving a node map associated with aparticular area, wherein the node map includes a plurality of nodes thatare each associated with a respective location within the particulararea; determining, between each node in the node map and at least oneother node in the node map, a likelihood that a particular user device,that is located in a location that is associated with the each node,will move to a location that is associated with the at least one othernode; receiving a request to navigate the particular user device from afirst location, in the particular area, to a second location in theparticular area; generating, based on the request and the determinedlikelihoods, navigation instructions from the first location to thesecond location; and outputting the generated navigation instructionsvia one or more display devices.
 16. The method of claim 15, wherein thelikelihood, that the particular user device will move from a first nodeto a second node, of the plurality of nodes, is based on historicalinformation associated with the particular user device.
 17. The methodof claim 15, wherein the likelihood, that the particular user devicewill move from a first node to a second node, of the plurality of nodes,is based on historical information associated with one or more otheruser devices.
 18. The method of claim 15, further comprising: generatinga visual representation of the particular area, the visualrepresentation including a graphical icon for each node, of theplurality of nodes; receiving information indicating that the particularuser device is located within a threshold distance of a boundary of theparticular area, and outputting, based on the information indicatingthat the particular user device is located within the threshold distanceof the boundary of the particular area, the visual representation of theparticular area to the particular user device.
 19. The method of claim15, further comprising: generating a visual representation of theparticular area, the visual representation including a selectablegraphical icon for at least one node, of the plurality of nodes;outputting the visual representation of the particular area to theparticular user device; and receiving a selection, from the particularuser device, of a particular selectable graphical icon associated with aparticular node, wherein the second location, indicated in the request,is associated with the selected particular node.
 20. The method of claim15, wherein the second location is associated with a particular room inthe particular area, the method further comprising: determining that thenavigation instructions have been completed; comparing a route taken,during the navigation, to the navigation instructions; determining thatthe route taken was different from the navigation instructions; andmodifying at least one of the likelihoods, between at least two of thenodes in the node map, based on the route taken being different from thenavigation instructions.